|
Host-based zoning can include WWN or LUN masking, and is typically known as “persistent binding.” In storage networking, ”persistent binding” is an option of zoning. Host-based zoning is usually referred to as persistent binding or LUN,〔mapping〕 and is perhaps the least implemented form of zoning. Because it requires the host configuration to be correct in order to avoid zoning conflicts, this form of zoning creates a greater opportunity for administrative errors and conflicting access to targets. Moreover zoning interfaces vary among different host operating systems and HBA's — increasing the possibility for administrative errors. If a host is not configured with the zoning software, it can access all devices in the fabric and create an even higher probability of data corruption. Host-based zoning is often used when clusters are implemented to control the mapping of devices to specific〔SCSI〕 target IDs. However, it should never be the only form of zoning. Augmenting host-based zoning with storage- and fabric-based zoning is the only acceptable method to reliably control device access and data security. Basically, A given LUN has it SCSI id assigned by its RAID device (typically a SAN ). But for some purposes it's useful to have the SCSI id assigned by the host itself: that's persistent binding. ==What is Persistent binding for ?== Without persistent binding, after every reboot, the SCSI id of a LUN may change. For Example, under Linux, a LUN bound on /dev/sda could migrate to /dev/sdb after a reboot. The risks augments with multipathing. Based on that, it is obvious that many software may crash without persistent binding. from http://www.storagesearch.com/datalink-art1.html :''Operating systems and upper-level applications (such as backup software) typically require a static or predictable SCSI target ID for their storage reliability and persistent binding affords that happening.'' 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Persistent binding」の詳細全文を読む スポンサード リンク
|